Now log into your new FreePBX system and it will show the Apply Config warning.

Do so.

0_1486444059378_upload-fea00064-3888-40ea-af94-ee5a8ca2979c

At this point you can go through the new system one piece at a time and make sure you are good.
Change a couple extensions to point to your new PBX and make sure they register and can call each other.
Once you are sure that the basics are working, disable the trunks on the old system, enable on the new system, and verify outside connectivity works.
Finally, you can change the rest of the extensions.

@poorizad said in Storing Elastix 2 Call Recordings on NFS NAS Share:

@scottalanmiller hi again....i guess the nfs drive is unmount from the server, because no file record on Nas after the 2016/07/28.....nothing changed on settings.....but a few server shutdown for hardware maintenance.....how can i fix it again ?

Try the mount command again. It might mount right up. If the NFS server has restarted, it would disconnect.

@poorizad said in Storing Elastix 2 VoiceMails on NFS NAS Share:

@scottalanmiller it means i use your previous command with this path . right ?

Correct

Long ago I had an article on this on my own blog but that is no longer up, so I am copying it here...

https://web.archive.org/web/20150221062029/http://www.scottalanmiller.com/linux/2012/09/02/improving-elastix-memory-usage/

The default installation of Elastix has more services running than are typically needed or desired on a PBX. These services eat far more memory that is necessary and can very easily be cleaned up to improve memory utilization.

First we will stop a series of unnecessary services from starting at boot time (this will disable shared storage, local email handling, new hardware detection, etc. so be aware that this does stop some things but any service that proves to be needed is trivial to re-enable.)

chkconfig nfslock off chkconfig cyrus-imapd off chkconfig iscsi off chkconfig iscsid off chkconfig netfs off chkconfig kudzu off

Further, if your system is like mine you likely use the web server very lightly but will find that the default configuration of Apache is set to spawn, by default, eight processes. This is far too many for a normal deployment. Each process uses memory. For an average deployment of Elastix, three is more than enough. You need only raise this number if web performance suffers. This will not impact telephony performance regardless.

In the file /etc/httpd/conf/httpd.conf we need to edit the section:

<IfModule prefork.c> StartServers 2 MinSpareServers 2 MaxSpareServers 8 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 4000 </IfModule>

to something more like this:

<IfModule prefork.c> StartServers 3 MinSpareServers 2 MaxSpareServers 10 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 4000 </IfModule>

You can wait for the system to reboot or restart Apache manually:

service httpd restart

And finally, to control swapping activity on the box, assuming that you want to avoid swapping when unnecessary, which I do because my box is virtualized, simply add this line on to /etc/sysctl.conf:

vm.swappiness = 10

You’ll want to test that number carefully. A setting of “10” is quite standard for virtualized systems. The default is “60”. For a physical deployment the higher value is likely better as it allows CentOS to make better decisions about how to utilize memory for maximum throughput. But on a virtualized system we really want to avoid, typically, any additional contention at the storage IO layer.
[Testing on Elastix 2.0 and 2.3]